Processing mobile banking transactions using a remote management server

ABSTRACT

A method and system for customizing a mobile application running on a mobile communication device of a user. In one implementation, the method includes providing the mobile application to the mobile communication device of the user, the mobile application having a generic platform; determining a special interest group (SIG) that is affiliated with the user; and customizing the generic platform of the mobile application based on information specific to the special interest group (SIG) that is affiliated with the user.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation and claims priority to U.S. patentapplication Ser. No. 17/009,356 filed Sep. 1, 2020 titled “PROCESSING AMOBILE BANKING TRANSACTIONS USING A NON-BROWSER BASED APPLICATION” whichis a continuation and claims priority to U.S. patent application Ser.No. 16/796,892 filed Feb. 20, 2020 titled “PROCESSING MOBILE BANKINGTRANSACTIONS” now U.S. patent Ser. No. 10/769,656 which is acontinuation and claims priority to U.S. patent application Ser. No.16/457,874 filed Jun. 28, 2019 titled “DISPLAYING AN ADVERTISEMENT INRESPONSE TO USER INPUT USING A NON-BROWSER BASED APPLICATION” now U.S.Pat. No. 10,621,612 which is a continuation and claims priority to U.S.patent application Ser. No. 15/980,735 filed May 15, 2018 titled,“SELECTING AND TRANSMITTING AN ADVERTISEMENT FROM A REMOTE MANAGEMENTSERVER” now U.S. Pat. No. 10,339,556 which is a continuation and claimspriority to U.S. patent application Ser. No. 15/134,101 filed Apr. 20,2016, titled REMOTE DELIVERY OF ADVERTISEMENTS now U.S. Pat. No.9,996,849 which is a continuation and claims priority to U.S. patentapplication Ser. No. 14/180,562, filed Feb. 14, 2014, titled “CUSTOMIZEDINFORMATION WITHOUT AUTHENTICATION” which is a continuation and claimspriority to U.S. patent application Ser. No. 11/956,261, filed Dec. 13,2007, titled “METHOD AND SYSTEM FOR DELIVERING CUSTOMIZED INFORMATION TOA MOBILE COMMUNICATION DEVICE BASED ON USER AFFILIATIONS” now U.S. Pat.No. 8,693,995, which is incorporated by reference herein in itsentirety.

FIELD OF INVENTION

The present invention relates to data communications and wirelessdevices.

BACKGROUND OF THE INVENTION

Mobile communication devices—e.g., cellular phones, personal digitalassistants, and the like—are increasingly being used to conduct paymenttransactions (e.g., through mobile wallet applications) as described inU.S. patent application Ser. No. 11/933,351, entitled “Method and SystemFor Scheduling A Banking Transaction Through A Mobile CommunicationDevice”, and U.S. patent application Ser. No. 11/467,441, entitled“Method and Apparatus For Completing A Transaction Using A WirelessMobile Communication Channel and Another Communication Channel, both ofwhich are incorporated herein by reference. Such payment transactionscan include, for example, purchasing goods and/or services, billpayments, and transferring funds between bank accounts.

In the mobile communication device space, delivering separate,customized mobile applications to mobile communications devices can bequite expensive in terms of cost and memory. For example, in the UnitedStates, AT&T recently announced that their mobile communication deviceplatform will only support up to two mobile wallet applications. Suchconstraints, as well as limited device memory, limit the number ofcustomized applications that an end user can run on a mobilecommunication device.

BRIEF SUMMARY OF THE INVENTION

In general, in one aspect, this specification describes a method forcustomizing a mobile application running on a mobile communicationdevice of a user. The method includes providing the mobile applicationto the mobile communication device of the user, the mobile applicationhaving a generic platform; determining a special interest group (SIG)that is affiliated with the user; and customizing the generic platformof the mobile application based on information specific to the specialinterest group (SIG) that is affiliated with the user.

Particular implementations can include one or more of the followingfeatures. Customizing the generic platform of the mobile application cancomprise displaying one or more of a logo, advertisement, coupon, alert,notification, or map that is associated with the special interest group(SIG) through the mobile application running on the mobile communicationdevice. The special interest group (SIG) can be one of a university,corporation, military, government, sports team, or alumni association.The generic platform of the mobile application can be customizable by aplurality of different special interest groups (SIGs). The genericplatform of the mobile application can comprise a generic user interfacehaving default screens, controls, or logos that are changeable based onan affiliation of the user to the plurality of different specialinterest groups (SIGs). Customizing the generic platform of the mobileapplication can comprise updating only content that is being displayedthrough the mobile application. Customizing the generic platform of themobile application can comprise customizing a number of modules that arepresented to users through the mobile application. The modules cancomprise one or more of a money management module that permits a user toaccess account information from a financial institution, a what's nearbymodule that permits a user to find points of interest (POI) anddirections, a rewards module that permits a user to keep track of rewardor loyalty cards, a ticket module that permits a user to purchase aticket for an event, and an options module that permits a user to changethe look-and-feel of the mobile application. The mobile communicationdevice can be one of a cellular phone or a wireless personal digitalassistant (PDA).

In general, in another aspect, this specification describes a systemincluding a management server to provide a mobile application to amobile communication device of a user, in which the mobile applicationhas a generic platform. The management server further determines aspecial interest group (SIG) that is affiliated with the user, andcustomizes the generic platform of the mobile application based oninformation specific to the special interest group (SIG) that isaffiliated with the user.

The details of one or more implementations are set forth in theaccompanying drawings and the description below. Other features andadvantages will be apparent from the description and drawings, and fromthe claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a block diagram of a communication system including amobile communication device and a management server in accordance withone implementation.

FIG. 2 illustrates one implementation of the mobile communication deviceof FIG. 1.

FIG. 3 illustrates one implementation of a method for customizing amobile application running on a mobile communication device.

FIG. 4 illustrates a block diagram of a communication system including amobile communication device and a management server in accordance withone implementation.

FIG. 5 illustrates one implementation of a method for customizing amobile application with a custom/affiliate logo of a special interestgroup (SIG).

FIG. 6 illustrates an example custom/affiliate logo of a specialinterest group (SIG) that can be displayed on a mobile communicationdevice.

FIG. 7 illustrates example advertisements/coupons of a special interestgroup (SIG) that can be displayed on a mobile communication device.

FIG. 8 illustrates example messages of a special interest group (SIG)that can be displayed on a mobile communication device.

FIG. 9 illustrates example maps of a special interest group (SIG) thatcan be displayed on a mobile communication device.

FIGS. 10A-10F illustrate example customization of a mobile applicationrunning on a mobile communication device.

FIG. 11 illustrates a block diagram of a communication system includinga wireless mobile communication device and a management server inaccordance with one implementation.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 illustrates one implementation of a communication system 100. Thecommunication system 100 includes a hand-held, wireless mobilecommunication device 102 a point-of-sale device 104 and a managementserver 106. In one implementation, the mobile communication device 102includes a mobile application (discussed in greater detail below) thatpermits a user of the mobile communication device 102 to conduct paymenttransactions. Payment transactions can include, for example, usingcontactless payment technology at a retail merchant point of sale (e.g.,through point of sale device 104), using mobile/internet commerce (e.g.,purchase tickets and products, etc.), storage of payment information andother digital artifacts (e.g., receipts, tickets, coupons, etc.),storage of banking information (payment account numbers, security codes,PIN's, etc.), and accessing banking service (account balance, paymenthistory, bill pay, fund transfer, etc.), and so on. The mobilecommunication device 102 can be a cellular phone, a wireless personaldigital assistant (PDA), or other wireless communication device.

FIG. 2 illustrates one implementation of the mobile communication device102. The mobile communication device 102 includes a mobile application200 that (in one implementation) is provided to the mobile communicationdevice 102 through a remote server (e.g., management server 106). In oneimplementation, the mobile application is a mobile wallet application(e.g., the Blaze Mobile Wallet application) available from Mobile CandyDish, Inc., of Alameda, Calif. In one implementation, the mobileapplication is a hosted service, as described in U.S. patent applicationSer. No. 11/939,821, entitled “Method and System For SecuringTransactions Made Through a Mobile Communication Device”, which isincorporated herein by reference. In one implementation, the mobileapplication 200 is configured to send requests to the management serverfor artifacts based on user input, e.g., received though a keypad (notshown) of the mobile communication device 102. Requests to themanagement server 106 can also be automated, via proximity-basedservices, e.g., consumer tapping (or in close proximity) anLBS/contactless/RFID enabled phone against a smart poster(RFID/Bluetooth/LBS enabled, etc.), kiosk, or other device.

As shown in FIG. 2, the mobile application 200 includes a user interface202 that is displayable on a display of the mobile communication device102. In one implementation, the user interface 202 is a generic userinterface (or platform) that can be customized based on one or morespecial interest groups (SIG) that are affiliated with a user of themobile communication device 102. In general, the user interface 202 canbe customized to display, e.g., screens, logos, messages, maps, coupons,advertisements, and other information, as discussed in greater detailbelow. In one implementation, a special interest group (SIG) is anorganization. For example, a special interest group can be a university,corporation, military, government, sports team, alumni association, andthe like. These (and other SIGs) generally have a need to brand andcustomize mobile applications they either sponsor or associate theirname to. This is mandated because SIGs tend to heavily invest inpromoting their name and brand recognition. Co-branding the mobileapplication with well-known third party brands will facilitate communityexposure, help drive consumer acceptance and adoption through viralmarketing (inherent to the community) as well as marketing programs bythe SIG.

Usually, the format used by the mobile application 200 remainsreasonably constant over time in contrast to content, which typicallychanges on a regular basis based on time and the SIG. In oneimplementation, as content changes on a regular basis, a SIG uploadsonly the new content to the management server (e.g., management server106). Accordingly, when the mobile application 200 next accesses thecontent of the management server 106, the management server 106 uploadsthe new (customized SIG) content (and format if applicable) to themobile application 200. Subsequent uploads to the mobile application 200can include only content since the format, in one implementation, iscached on the mobile communication device 102 after the first download.If the SIG desires to change the format at a subsequent time, the nextupload to the mobile application 200 can include both the new layoutformat and any new content.

In one implementation, the mobile application 200 comprises a pluralityof different modules, in which each module provides a specific functionfor a user. For, example, the Blaze Mobile Wallet application providesthe following example modules:

-   -   Money Management—A user can access account information (e.g.,        balance, transaction history, and so on) from banks and credit        card financial institutions. A user can also pay bills, transfer        funds (e.g., person-to-person, me-to-me same bank, and me-to-me        different bank). A user can also have their paychecks directly        deposited into in their mobile wallet, withdraw cash from ATM        machines, or pick up cash at a redemption location. A user can        also use a contactless debit card associated with their mobile        wallet to buy products at participating contactless merchants        and receive their transaction history in their mobile wallet in        real-time.    -   What's Nearby—A user can find points of interest (POI),        directions, and access maps using this module. For example, a        user can find points of interest from over a dozen categories        such as restaurants, shopping malls, golf courses, gas stations,        regular merchants, theaters, ATM locations, and so on. With        respect to directions and maps, a user can get turn-by-turn        directions and a viewable map with zooming capability.    -   Rewards/Loyalty/Coupons—A user can keep track of reward/loyalty        cards—e.g., frequently flyer account number, rental car reward        membership, hotel reward membership, and the like—through the        rewards module. In one implementation, a user can view, in        real-time, a summary of all rewards (e.g., points accumulated)        directly on a cellular phone. A user can also search for and        store coupons on their mobile communication device for use        during, e.g., a contactless purchase.    -   Tickets—This module permits a user to purchase tickets for e.g.,        movies, sport events, and other entertainment events, through        their mobile communication device. A user can also view movie        trailers and read reviews through their mobile communication        device.    -   Options—Through this module a user can customize the look and        feel of the mobile application, including setting the colors,        graphics, logos, and so on. A user can also set a default        payment method, send feedback, tell-a-friend, earn reward        points, and the like.

The modules above are example modules. The mobile application canprovide other modules to perform additional functions for a user over amobile communication device—e.g., an additional module can include anInternet Purchase module that permits users to use their mobilecommunication device to purchase items over the Internet. In oneimplementation, a special interest group (SIG) can modify the number ofmodules that are available to a user (or users). For example, aparticular special interest group (SIG) may only want to provide arewards program to users, and therefore, the special interest group(SIG) can modify the mobile application 200 to present only a rewardsmodule as described above. In general, a special interest group (SIG)can modify the mobile application 200 to provide any number andcombination of modules to users.

FIG. 3 illustrates a method 300 for customizing a mobile application(e.g., mobile application 200) running on a mobile communication device.(e.g., mobile communication device 102). A mobile application having ageneric platform is provided to a mobile communication device of a user(step 302). In one implementation, the mobile application is provided tothe mobile communication device through a network—e.g., a public network(e.g., the Internet), a private network, or a voice communicationsnetwork. The generic platform can comprise a generic user interfacehaving default screens, controls, and/or logos. A determination is made(e.g., by management server 106) of one or more special interest groups(SIGs) that are associated with the user (step 304). In oneimplementation, the management server 306 queries a database (e.g., anaffiliate content database) to determine which special interest groups(SIGs) that a given user is associated with. The generic platform of themobile application is customized based on one or more of the specialinterest groups (SIGs) that are associated with the user (step 306).

In one implementation, association between a SIG and an end user isvalidated via an out-of-band process—e.g., a banking customer may haveto specify their SIG and provide their SIG credentials (e.g., onlinebanking userID/password) that are unique to the SIG. The managementserver validates the credentials with the SIG. Once the end user hasbeen authenticated by the SIG, it will be possible to deliver the SIG'sbranding and messaging specifically to the end user. Such a techniqueminimizes the number of applications that need to be executed by amobile communication device. For example, a single mobile applicationcan be customized by a large number of different special interest groups(SIGs). In one implementation, the mobile application can be customizedto display different screens, user interfaces and/or controls. Lessmemory is, therefore, required by a mobile communication device in orderto support applications required by multiple special interest groups(SIGs).

FIG. 4 illustrates one implementation of a communication system 400. Thecommunication system 400 includes a hand-held, wireless mobilecommunication device 402, a management server 404, a user portal 406,and a special interest group (SIG) portal 408. In one implementation,the management server 404 is coupled to a user and profile database 410,an affiliate content database 412, and an integrated marketing database414. In one implementation, the user and profile database 410 storesuser profile information associated with each user—e.g., passwords,personal identification numbers (PINs), contact information, e-mailaddresses, and the like; the affiliate content database 412 storesassociations between special interest groups (SIGs) and users; and theintegrated marketing database 414 stores artifacts (e.g., coupons,advertising, tickets, etc.) that can be sent to a user.

To enable the branding and customization of the mobile application(e.g., the mobile wallet application) running on the mobilecommunication device 402, in one implementation, various screens aredesigned based on meta-data (i.e., meta-data delivered (pulled orpushed) to the mobile communication device 402 based on the SIG). Thecore wallet screen can be the same for all subscribers—e.g., a loginscreen for all subscribers can have the same pre-defined format(controlling how content is displayed and permitted actions), and onlythe content is dynamically generated. The following screens, or categoryof screens, include (but are not limited to):

-   -   Logo—A community logo will display upon wallet launch. If a        customer is not affiliated with a SIG, the default Blaze logo        will be displayed.    -   Watermark—An almost transparent watermark image that does not to        conflict with maps, wallpaper, etc.    -   Advertisements—Local advertisements from the community will be        displayed instead of or in addition to general advertisements.        If a customer is not affiliated with a SIG, general        advertisements will be displayed.    -   Coupons—Coupons from the local community will be displayed        instead of or in addition to general coupons. If a customer is        not affiliated with a SIG, general coupons will be displayed.    -   Events—Community events will be displayed. If a customer is not        affiliated with a SIG, general events will be displayed such as        information about MCD (Mobile Candy Dish), new wallet features,        etc.    -   Alerts—Community alerts will be displayed. If a customer is not        affiliated with a SIG, general alerts will be displayed.    -   Maps—A community map will be displayed. Some examples of a        community map include a campus map for a university, seating        chart for a sports team, corporate campus map (particularly for        large campuses like Google, Microsoft, etc.), and so forth.

In some cases, a special interest group (SIG) may be involved in thecontent approval process. In such an implementation, in order to delivermeta-data to the mobile communication device based on input from theSIG, the end-user's account (e.g., walletID, etc.) is associated with aSIG. The SIG will access a portal (web-based or otherwise) (e.g., SIGportal 408) that enables the SIG to control, publish, etc., contentassociated to the SIG on the management server 404. In oneimplementation, one or more screens queries the management server 404for dynamic content (media, text, logo, sort order, etc.). The query caninclude (but is not limited to) the end-users walletID. Using a look-uptable in the management server 404 or the affiliate content database412, it is possible to determine the associated SIG. The managementserver 404 can then internally determine the appropriate content(including media, etc.) to respond to the mobile application running onthe mobile communication device 402. These result sets can be cached onthe mobile communication device 402 for future use to improveperformance (as needed).

Logos

FIG. 5 illustrates a method 500 for providing a logo to a mobilecommunication device (e.g., mobile communication device 402) for displaythrough a mobile application running on the mobile communication device.An end user registers an affiliation with a special interest group (SIG)on a web portal (e.g., user portal 406) (step 502). Thereafter, the enduser logs into the mobile application running on the mobilecommunication device (step 504). Upon initial login, the mobileapplication displays a default logo (step 506). The mobile applicationqueries a management server (e.g., management server 404) for anycustom/affiliate logos that is associated with the user (step 508). Themanagement server determines which special interest groups (SIGs) thatthe user is affiliated with, and sends a custom/affiliate logo to themobile application running on the mobile communication device (step510). FIG. 6 illustrates an example logo of a University that can besent to a mobile application. In response to receiving thecustom/affiliate logo, the mobile application displays thecustom/affiliate logo (step 512). In one implementation, the defaultlogo is replaced with the custom/affiliate logo in response to the userlogging off, and re-logging into the mobile application.

Integrated Mobile Marketing Insertion

In one implementation, an advertising manager application running on themanagement server 404 inserts advertisements (based on advertisementinsertion order) into Ad Engine (or 3rdParty Ad Delivery platform). Theadvertising manager application specifies specific advertisements withtargeting parameters of special interest groups (SIGs) (among othertargeting parameters as specified by, e.g., an advertising agency) anddisplays these advertisements in the mobile application.

Integrated Mobile Marketing (Advertising and Coupons) Delivery

In one implementation, advertising and/or coupons can be sent to amobile application based on one or more special interest groups (SIGs)that a user is affiliated with. In one implementation, an end userregisters affiliation with a special interest group (SIG) through a webportal (e.g., user portal 406). The management system 406 can validatethe affiliation out-of-band. The end user logs into mobile application,and the mobile application queries the management server 404 for anyadvertisements or coupons by providing a screenID (a unique screenidentifier). The management server 404 determines that the user has anaffiliation to a special interest group (SIG) and appends the SIGID (aunique SIG identifier) to the target parameters. A query including thetargeting parameters is forwarded to an advertising engine (or3rdParty). The advertising engine responds with the appropriate URL tothe advertising object that best meets the advertising criteria (e.g.,age, gender, geographic location, proximity to retail store, shoppinglist, transaction history, etc). In one implementation, the mobileapplication queries advertisements based on the URL returned. FIG. 7illustrates example advertisements/coupons that can be displayed througha mobile application running on a mobile communication device.

Alerts and Notification

In one implementation, alerts and notifications can be sent to a mobileapplication based on one or more special interest groups (SIGs) that auser is affiliated with. In one implementation, a notification managerapplication running on the management server 404 inserts alerts (basedon an insertion order) into a notification engine associated with themanagement server 404 (or a third party notification delivery platform).The notification manager application associates the notifications (text,etc.) with one or more SIGIDs (among other targeting parameters asspecified by, e.g., an advertising agency). In one implementation, thenotification engine queries the user and profile database 410, anddetermines a list of walletIDs (of end users) that match the targetdelivery criteria. For each end-user identified, the management server404 determines a notification mode (e.g., SMS/text messaging, e-mail, orboth) and a delivery window (time of day, etc.). These criteria are usedto send the notification (or alerts) to the end-user. FIG. 8 illustratesexample alerts and notifications that can be displayed through a mobileapplication running on a mobile communication device.

Campus Maps

In one implementation, maps can be sent to a mobile application based onone or more special interest groups (SIGs) that a user is affiliatedwith. In one implementation, and end user registers affiliation with aspecial interest group (SIG) through a web portal (e.g., user portal406). The management system 404 can validate the affiliation of the userto the special interest group (SIG) out-of-band. The end user logs intothe mobile application, and the mobile application queries themanagement server 404 for an affiliate campus map. The management server404 determines that the end user has an affiliation with a specialinterest group (SIG), and responds to the query with a campus mapassociated with the special interest group (SIG). The campus map iscached in a memory of the mobile communication device 402, and themobile application running on the mobile communication device 402displays the campus map. FIG. 9 illustrates example maps/seating chartsthat can be displayed through a mobile application running on a mobilecommunication device.

FIGS. 10A-10F illustrate example screens, messages, advertisements,and/or coupons that can be displayed through a mobile applicationrunning on a mobile communication device. In particular, FIG. 10Aillustrates example customization of a mobile application for a bank;FIG. 10B illustrates example customization of a mobile application for auniversity; FIG. 10C illustrates example customization of a mobileapplication for a sports team; FIG. 10D illustrates examplecustomization of a mobile application for a credit union; FIG. 10Eillustrates example customization of a mobile application for acorporation; and FIG. 10F illustrates example customization of a mobileapplication for a military campus. In general, the same generic platformof a mobile application can be used to deliver the different screens,messages, advertisements, and/or coupons shown in FIGS. 10A-10F.

One or more of method steps described above can be performed by one ormore programmable processors executing a computer program to performfunctions by operating on input data and generating output. Generally,the invention can take the form of an entirely hardware embodiment, anentirely software embodiment or an embodiment containing both hardwareand software elements. In one implementation, the invention isimplemented in software, which includes but is not limited to firmware,resident software, microcode, etc. Furthermore, the invention can takethe form of a computer program product accessible from a computer-usableor computer-readable medium providing program code for use by or inconnection with a computer or any instruction execution system. For thepurposes of this description, a computer-usable or computer readablemedium can be any apparatus that can contain, store, communicate,propagate, or transport the program for use by or in connection with theinstruction execution system, apparatus, or device. The medium can be anelectronic, magnetic, optical, electromagnetic, infrared, orsemiconductor system (or apparatus or device) or a propagation medium.Examples of a computer-readable medium include a semiconductor or solidstate memory, magnetic tape, a removable computer diskette, a randomaccess memory (RAM), a read-only memory (ROM), a rigid magnetic disk andan optical disk. Current examples of optical disks include compactdisk-read only memory (CD-ROM), compact disk-read/write (CD-R/W) andDVD.

FIG. 5 illustrates a data processing system 1100 (e.g., a mobilecommunication device) suitable for storing and/or executing programcode. Data processing system 1100 includes a processor 1102 coupled tomemory elements 1104A-B through a system bus 1106. In otherimplementations, data processing system 1100 may include more than oneprocessor and each processor may be coupled directly or indirectly toone or more memory elements through a system bus. Memory elements1104A-B can include local memory employed during actual execution of theprogram code, bulk storage, and cache memories that provide temporarystorage of at least some program code in order to reduce the number oftimes the code must be retrieved from bulk storage during execution. Asshown, input/output or I/O devices 1108A-B (including, but not limitedto, keyboards, displays, pointing devices, etc.) are coupled to dataprocessing system 1100. I/O devices 1108A-B may be coupled to dataprocessing system 1100 directly or indirectly through intervening I/Ocontrollers (not shown).

In one implementation, a network adapter 1110 is coupled to dataprocessing system 1100 to enable data processing system 1100 to becomecoupled to other data processing systems or remote printers or storagedevices through communication link 1112. Communication link 1112 can bea private or public network. Modems, cable modems, and Ethernet cardsare just a few of the currently available types of network adapters.

Although the present invention has been particularly described withreference to implementations discussed above, various changes,modifications and substitutes are can be made. Accordingly, it will beappreciated that in numerous instances some features of the inventioncan be employed without a corresponding use of other features. Further,variations can be made in the number and arrangement of componentsillustrated in the figures discussed above.

What is claimed is:
 1. A method for processing a mobile bankingtransaction, comprising: receiving, at remote management server,information related to an identification code associated with a user andinformation related to a password from a non-browser based application,wherein the non-browser based application is a mobile operating systemplatform based mobile application with a graphical user interface thatis preinstalled or downloaded and installed on a mobile device, whereinthe graphical user interface includes a graphical icon, the mobiledevice including a mobile device display, a mobile device processor, amobile device memory, a mobile device radio transceiver that supportsvoice and data interactions through a first wireless communicationchannel, and a mobile device wireless fidelity (Wi-Fi) transceiver;authenticating a user associated with the identification code associatedwith the user and the information related to the password; after userauthentication, receiving, a request for the mobile banking transactionfrom the non-browser based application, wherein the non-browser basedapplication receives the request for the mobile banking transactionthrough user input via the mobile device display; after receiving therequest for the mobile banking transaction, transmitting the request forthe mobile banking transaction to a transaction server for processingthe request for the mobile banking transaction using a payment method;after the request for the mobile banking transaction has been processed,transmitting a digital artifact from the remote management server to thenon-browser based application which displays the digital artifact withinthe non-browser based application.
 2. The method of claim 1, wherein therequest for the mobile banking transaction comprises bill pay.
 3. Themethod of claim 1, wherein the request for the mobile bankingtransaction comprises transferring funds.
 4. The method of claim 1,wherein the request for the mobile banking transaction comprises viewingtransaction history.
 5. The method of claim 1, wherein the request forthe mobile banking transaction comprises viewing account balance.
 6. Themethod of claim 1, wherein the request for the mobile bankingtransaction comprises viewing reward points.
 7. The method of claim 1,wherein the request for the mobile banking transaction comprisesdepositing a check.
 8. The method of claim 1, wherein the request forthe mobile banking transaction comprises withdrawing cash from an ATMmachine.
 9. The method of claim 1, wherein the digital artifactcomprises one of a receipt, advertisement, coupon, ticket, media, orcontent.
 10. The method of claim 1, where the payment method is a bankaccount, credit card, debit card, or prepaid card.
 11. The method ofclaim 1, further wherein the non-browser based application receives thedigital artifact through a connection of the mobile device to a wirelessnetwork; the non-browser based application displays the digital artifactwhile the mobile device maintains the connection to the wirelessnetwork; and the method further comprises: losing the connection of themobile device to the wireless network while the non-browser basedapplication displays the digital artifact; and after losing theconnection, continuing to display the digital artifact within thenon-browser based application.
 12. The method of claim 1, furtherwherein upon the condition that the mobile device loses connection witha wireless network the non-browser based application monitors for accessto the wireless network and automatically re-connects to the wirelessnetwork when the wireless network is available.
 13. The method of claim1, further wherein the non-browser based application sends a request tothe remote management server to retransmit the digital artifact if ithas not received the digital artifact from the remote management serverwithin a certain period of time.
 14. The method of claim 1, furtherwherein no sensitive data is stored on the mobile device.
 15. The methodof claim 14, wherein the sensitive data is information related to thepayment method.
 16. The method of claim 1, further wherein thenon-browser based application automatically displays the digitalartifact in an easily retrievable format.
 17. The method of claim 1,further wherein the non-browser based application is configured to use astructured format, wherein the structured format means the non-browserbased application can store and display the digital artifact in anorganized manner.
 18. The method of claim 1, further wherein the remotemanagement server is configured to store a single identification codeassociated with a user for a plurality of mobile devices, and furtherwherein the configuration means the remote management server scales. 19.The method of claim 1, further wherein the information related to thepassword is information related to a personal identification number(PIN).
 20. The method of claim 1, further, wherein the informationrelated to the password is information related to biometric data.
 21. Aremote management server for processing a mobile banking transaction,the mobile device comprising: a remote management server input interfaceconfigured to: receive information related to an identification codeassociated with a user and information related to a password from anon-browser based application, wherein the non-browser based applicationis a mobile operating system platform based mobile application with agraphical user interface that is preinstalled or downloaded andinstalled on the mobile device, wherein the graphical user interfaceincludes a graphical icon, the mobile device including a mobile devicedisplay, a mobile device processor, a mobile device memory, a mobiledevice radio transceiver that supports voice and data interactionsthrough a first communication channel and a mobile device wirelessfidelity (Wi-Fi) transceiver; after user authentication, receive arequest for the mobile banking transaction from the non-browser basedapplication, wherein the non-browser based application receives therequest for the mobile banking transaction through user input via themobile device display; a mobile device processor configured to:authenticate the user associated with the information related to theidentification code associated with the user and the information relatedto the password; a mobile device output interface configured to: afterreceiving the request for the mobile banking transaction, transmit therequest for the mobile banking transaction from the remote managementserver to a transaction server for processing the request for the mobilebanking transaction using a payment method; and after the request forthe mobile banking transaction has been processed, transmit a digitalartifact from the remote management server to the non-browser basedapplication which displays the digital artifact within the non-browserbased application.
 22. The remote management server of claim 21, whereinthe request for the mobile banking transaction comprises bill pay. 23.The remote management server of claim 21, wherein the request for themobile banking transaction comprises transferring funds.
 24. The remotemanagement server of claim 21, wherein the request for the mobilebanking transaction comprises viewing transaction history.
 25. Theremote management server of claim 21, wherein the request for the mobilebanking transaction comprises viewing account balance.
 26. The remotemanagement server of claim 21, wherein the request for the mobilebanking transaction comprises depositing a check.
 27. The remotemanagement server of claim 21, wherein the request for the mobilebanking transaction comprises withdrawing cash from an ATM machine. 28.The remote management server of claim 21, wherein the digital artifactcomprises one of a receipt, advertisement, coupon, ticket, media, orcontent.
 29. The remote management server of claim 21, wherein thedigital artifact comprises one of a receipt, advertisement, coupon,ticket, media, or content.
 30. The remote management server of claim 21,where the payment method is a bank account, credit card, debit card, orprepaid card.
 31. The remote management server of claim 21, furtherwherein the non-browser based application receives the digital artifactthrough a connection of the mobile device to a wireless network; thenon-browser based application displays the digital artifact while themobile device maintains the connection to the wireless network; and themethod further comprises: losing the connection of the mobile device tothe wireless network while the non-browser based application displaysthe digital artifact; and after losing the connection, continuing todisplay the digital artifact within the non-browser based application.32. The remote management server of claim 21, further wherein thenon-browser based application monitors for access to a wireless networkand automatically reconnects to the wireless network when the wirelessnetwork is available.
 33. The remote management server of claim 21,further wherein the non-browser based application sends a request to theremote management server to retransmit the digital artifact if it hasnot received the digital artifact from the remote management serverwithin a certain period of time.
 34. The remote management server ofclaim 21, further wherein no sensitive data is stored on the mobiledevice.
 35. The remote management server of claim 34, wherein thesensitive data is information related to the payment method.
 36. Theremote management server of claim 21, further wherein the non-browserbased application automatically displays the digital artifact in aneasily retrievable format.
 37. The remote management server of claim 21,further wherein the non-browser based application is configured to use astructured format, wherein the structured format means the non-browserbased application can store and display the digital artifact in anorganized manner.
 38. The remote management server of claim 21, furtherwherein the remote management server is configured to store a singleidentification code associated with a user for a plurality of mobiledevices, and further wherein the configuration means the remotemanagement server scales.
 39. The remote management server of claim 21,further wherein the information related to the password is informationrelated to a personal identification number (PIN).
 40. The remotemanagement server of claim 21, further, wherein the information relatedto the password is information related to biometric data.